Closed
Description
Is there a way to show the file path of where it is downloading Chromium when running npm i puppeteer as I can't seem to ever find where it actually is downloading it
Is there a way to show the file path of where it is downloading Chromium when running npm i puppeteer as I can't seem to ever find where it actually is downloading it
Activity
ebidel commentedon Sep 4, 2017
The path will change based on the platform that you install puppeteer on. install.js has methods for finding that path. Something like this should work:
info.executablePathwill give you the binary's path. Useful when launching chrome:puppeter.launch({executablePath: info.executablePath}).Output path as chromium gets successfully downloaded
Output path as chromium gets successfully downloaded (#689)
KaKi87 commentedon May 1, 2020
Hello, how can I do the same thing today ? The
utilsdirectory no longer exists. Thanksmathiasbynens commentedon May 4, 2020
@KaKi87 https://github.com/puppeteer/puppeteer/blob/master/src/BrowserFetcher.ts
prvnsmpth commentedon May 16, 2020
@KaKi87 Puppeteer has an API for getting the path to the executable: https://github.com/GoogleChrome/puppeteer/blob/v1.1.1/docs/api.md#puppeteerexecutablepath
humkins commentedon Oct 11, 2022
run in the directory where
node_modulesis locatednode -e "console.log(require('puppeteer').executablePath())"Example output on Linux:
Buscando arreglar arranque en gitlab con base en puppeteer/puppeteer#679
estatistics commentedon Oct 3, 2023
downloaded location in debian linux for chrome is
/home/user/.cache/puppeteer/chrome/linux-117.0.5938.92/chrome-linux64/and it is not detected at all. I will recommend puppeeteer to tell the EXPECTED full dir in order to be able to rename it for that.